Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: URI components are not encoded correctly (#1640) #1641

Merged
merged 5 commits into from
May 3, 2024

Conversation

Thomas-Bergmann
Copy link
Contributor

@Thomas-Bergmann Thomas-Bergmann commented Apr 23, 2024

  • encode all URI components
  • only constants doesn't need to be encoded

PR Type

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] CI-related changes
[ ] Documentation content changes
[ ] Application / infrastructure changes
[ ] Other:

What Is the Current Behavior?

Issue Number: Closes #1640

What Is the New Behavior?

Does this PR Introduce a Breaking Change?

The PR provides a central function to select two behavior:

  • duplicated component encoding (for former ICM releases)
  • single component encoding (for future fixed versions)

see encodeResourceID at src/app/core/utils/url-resource-ids.ts
[] Yes
[X] No

Other Information

To be able to use "single" encoded URI components a new versions of ICM application server and HTTPD configuration are necessary.
ICM-AS fix required - removes duplicate decoding (12.0.0)
ICM-WA fix required - allow encoded slashes in URIs

AB#96081

@Thomas-Bergmann Thomas-Bergmann changed the title WIP: fix: URI components are not encoded correctly (#1640) fix: URI components are not encoded correctly (#1640) Apr 30, 2024
@shauke shauke added this to the 5.2 milestone May 3, 2024
shauke
shauke previously approved these changes May 3, 2024
Thomas-Bergmann and others added 5 commits May 3, 2024 14:36
* only constants doesn't need to be encoded

The URI component will be done by encodeResourceID.
In case ICM is fixed the project can change it to single encoding at one place.
* using encodeResourceID in the tests too allows a single switch at that function.
@shauke shauke force-pushed the fix/1640-EncodeURIComponents branch from 0ef6c44 to 9fafc13 Compare May 3, 2024 12:48
@shauke shauke merged commit 3e7c0ae into develop May 3, 2024
22 checks passed
@shauke shauke deleted the fix/1640-EncodeURIComponents branch May 3, 2024 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

PWA doesn't encode URI components correctly.
2 participants